Skip to content

[SYCL] Extract sycl-post-link utilities to SYCLPostLink library#21678

Open
maksimsab wants to merge 2 commits intointel:syclfrom
maksimsab:refactor_sycl_post_link_utils
Open

[SYCL] Extract sycl-post-link utilities to SYCLPostLink library#21678
maksimsab wants to merge 2 commits intointel:syclfrom
maksimsab:refactor_sycl_post_link_utils

Conversation

@maksimsab
Copy link
Copy Markdown
Contributor

Move file I/O and module processing utilities from sycl-post-link tool to new Utils.h/cpp. Extracts saveModuleIR, saveModuleProperties, saveModuleSymbolTable, and isTargetCompatibleWithModule functions.

Move file I/O and module processing utilities from sycl-post-link tool
to new Utils.h/cpp. Extracts saveModuleIR, saveModuleProperties,
saveModuleSymbolTable, and isTargetCompatibleWithModule functions.

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
@maksimsab maksimsab requested a review from a team as a code owner April 2, 2026 13:31
// SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
//
//===----------------------------------------------------------------------===//
// See comments in the header.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why not just duplicate the string that is in the header.

Suggested change
// See comments in the header.
// Low-level utility functions for SYCL post-link processing.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LLVM Coding standards specifically says not to do that:
Don’t duplicate the documentation comment in the header file and in the implementation file

https://llvm.org/docs/CodingStandards.html#doxygen-use-in-documentation-comments

However, both approaches are met in the codebase. I don't object of duplicating this comment.

@maksimsab
Copy link
Copy Markdown
Contributor Author

@intel/llvm-gatekeepers Could we please merge that?

@sarnex
Copy link
Copy Markdown
Contributor

sarnex commented Apr 7, 2026

@maksimsab This PR needs conflicts resolved after merging the other one

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants